Let journal entries be edited in the TUI - #266

Before

Journal reader selects a day
└── Reads the entry
    └── ❌ No TUI write path

After

Journal reader selects a day
└── Presses e
    └── Edits the selected day
        └── Presses ctrl+s
            └── ✅ Entry is created, updated, or removed  ← CHANGED

The form uses e to edit, ctrl+s to save, and esc to cancel. An empty save mirrors hey journal write by removing the day’s entry.

• ✅ Focused journal tests cover form routing, create/update/removal, repeated wrapper-free save cycles, rich HTML and attachment preservation, literal plain-text fallback, failed reads, failed saves, help bindings, and notice layout.
• ✅ Three no-op edit/save cycles against a real journal reduced three accumulated trix-content wrappers to the server’s single presentation wrapper and kept the normalized text unchanged.
• ✅ Interaction recording shows opening the selected day with e, editing it without presentation wrappers, saving with ctrl+s, and repeating an unchanged save without wrapper growth.

GOWORK=off go test ./internal/tui -run 'TestJournal' -count=1
ok github.com/basecamp/hey-cli/internal/tui

GOWORK=off make test
PASS

GOWORK=off make lint
0 issues

GOWORK=off make fmt-check vet tidy-check
PASS

Included: TUI editing for the selected journal day, successful-save refresh, stable removal of trix-content presentation wrappers before updates, rich-content preservation, and recoverable save errors.

Not included: a rich-text terminal editor or SDK/API changes. Existing CLI journal behavior is unchanged.

The change uses the existing Journal().Get and Journal().Update operations. Rollback is a code revert.

Rich entries appear as editable HTML without HEY’s trix-content presentation containers, so repeated unchanged saves retain links, formatting, and attachments without accumulating wrappers. Review should begin with that token-preserving normalization and with failed-read and failed-save handling before the form lifecycle.

1. internal/tui/journal.go — read/write flow and request-lane handling
2. internal/tui/journal_form.go — textarea behavior and key bindings
3. internal/tui/journal_test.go — behavioral and failure-state evidence

Origin and supporting links: Basecamp card